Is this going to create another process providing only HTTP API for data created by another already running Station Core process? That seems like too many processes to me!

IMO, --listen should be an optional argument for the default command (station) that runs the main station process & modules.

Maybe instead of --listen argument, we can implement the following flag:

• If PORT is set to some value (including 0), we start the HTTP server
• If PORT is not specified, we don't create any server.

It's less explicit than --listen, so maybe it's not a good idea. Posting it just for consideration.

Good point, it's not a command it's just an option, meaning that it will run the basic $ station command, but also open an HTTP server.

IMO, --listen should be an optional argument for the default command (station) that runs the main station process & modules.

That's exactly how it is, I'm going to improve the README.

It's less explicit than --listen, so maybe it's not a good idea. Posting it just for consideration.

Those are my conerns as well. And we do read $PORT already, but only if --listen is set.

These two options are relevant only to station; they don't apply to station metrics and friends, right?

I also don't see the --port argument defined anywhere in bin/station.js.

Oh, that's outdated. Will fix!